Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3b9da90e58df35a8df65f96fa857ac3f048a904c8eb56914dde78f1c9600cc3

Tx prefix hash: 276fe14563830bbc3b3697f0f68ce50ac46551c546e2d9c936e1db66a8ee252d
Tx public key: 72607c5225c6cbcbdf8e90a927b52860abf8153f3805bf8323b59e995503effc
Timestamp: 1747227106 Timestamp [UCT]: 2025-05-14 12:51:46 Age [y:d:h:m:s]: 00:238:05:08:17
Block: 1282759 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168030 RingCT/type: yes/0
Extra: 0172607c5225c6cbcbdf8e90a927b52860abf8153f3805bf8323b59e995503effc02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c5f9eee0175c430705e254768609498a6cdeb9ae1ebdffa1cb0e7b7a23dce5d 0.600000000000 1770170 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": 1282769, "vin": [ { "gen": { "height": 1282759 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c5f9eee0175c430705e254768609498a6cdeb9ae1ebdffa1cb0e7b7a23dce5d" } } ], "extra": [ 1, 114, 96, 124, 82, 37, 198, 203, 203, 223, 142, 144, 169, 39, 181, 40, 96, 171, 248, 21, 63, 56, 5, 191, 131, 35, 181, 158, 153, 85, 3, 239, 252, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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