Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0dc303e02a486236c78d9d564f8605c518c4c770ca02238f0d670de2bdaa228a

Tx prefix hash: 637918163191ea05d0d90a8edc2c09e04b3d108c2f278a21ee7c6253fa210503
Tx public key: 3151e22b7e506cb8516ada81fddaf3c972b167f6c6207942447933371db3c9a7
Timestamp: 1740644465 Timestamp [UCT]: 2025-02-27 08:21:05 Age [y:d:h:m:s]: 00:220:16:56:13
Block: 1228243 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155432 RingCT/type: yes/0
Extra: 013151e22b7e506cb8516ada81fddaf3c972b167f6c6207942447933371db3c9a7021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0057b8ae987e6c763399609c309ca1e9da0f4d98eef09e953c8433a7b50aa915 0.600000000000 1715120 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": 1228253, "vin": [ { "gen": { "height": 1228243 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0057b8ae987e6c763399609c309ca1e9da0f4d98eef09e953c8433a7b50aa915" } } ], "extra": [ 1, 49, 81, 226, 43, 126, 80, 108, 184, 81, 106, 218, 129, 253, 218, 243, 201, 114, 177, 103, 246, 198, 32, 121, 66, 68, 121, 51, 55, 29, 179, 201, 167, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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