Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 1b112470b0627377835973e1ddbbd09d3d6bc4c3ba1c7ffd7e4e8cc2858d2766

Tx prefix hash: fc320f7d665ba65cb3a8dacd27535878268d69addfcb336d67b6b8809ecc6420
Tx public key: 0d8c18fa381bd69f0a0ceacd2e92d81b1bbc409638cea75429f3e583c9734e42
Timestamp: 1707249178 Timestamp [UCT]: 2024-02-06 19:52:58 Age [y:d:h:m:s]: 01:137:08:05:04
Block: 951837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359046 RingCT/type: yes/0
Extra: 010d8c18fa381bd69f0a0ceacd2e92d81b1bbc409638cea75429f3e583c9734e4202110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b079ce76c2c68ac61e5e794d59df48cca29c24a536181d34e8404750286b0cdc 0.600000000000 1410669 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 951847, "vin": [ { "gen": { "height": 951837 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b079ce76c2c68ac61e5e794d59df48cca29c24a536181d34e8404750286b0cdc" } } ], "extra": [ 1, 13, 140, 24, 250, 56, 27, 214, 159, 10, 12, 234, 205, 46, 146, 216, 27, 27, 188, 64, 150, 56, 206, 167, 84, 41, 243, 229, 131, 201, 115, 78, 66, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8