Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef47745eb985a4807b39cb8e851f7d3c7e8cef1e2f4444a58f83802b8199397b

Tx prefix hash: fbaff3a7bc832d5b7acb7940a128fb724d4bf2afbf678a8a93de14dff6545a5d
Tx public key: c1cd8f832e5bda64fde2c771f2ed496d0d3d33018f8acd41e7baf74e8e073461
Timestamp: 1764118822 Timestamp [UCT]: 2025-11-26 01:00:22 Age [y:d:h:m:s]: 00:001:09:19:05
Block: 1420194 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 995 RingCT/type: yes/0
Extra: 01c1cd8f832e5bda64fde2c771f2ed496d0d3d33018f8acd41e7baf74e8e07346102110000000370609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d767753f8a4e1c389f23034f55ad40c7ebaf53abcdfc901d1b7802242a65761 0.600000000000 1908735 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": 1420204, "vin": [ { "gen": { "height": 1420194 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d767753f8a4e1c389f23034f55ad40c7ebaf53abcdfc901d1b7802242a65761" } } ], "extra": [ 1, 193, 205, 143, 131, 46, 91, 218, 100, 253, 226, 199, 113, 242, 237, 73, 109, 13, 61, 51, 1, 143, 138, 205, 65, 231, 186, 247, 78, 142, 7, 52, 97, 2, 17, 0, 0, 0, 3, 112, 96, 157, 3, 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