Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d2fb03b752eddf7c4c28a02f14cd4f0fd8eac6fe337de1a6a7742f98eb25045

Tx prefix hash: 62d2f7ca551c126f24aab5f763308b6ccd244c65ddde9ded0d2e724b70382eb9
Tx public key: 49d8a21f92fd8df81c6d89ad8a7718104bdb4953a6cfc3d872a0fbd534624d81
Timestamp: 1707661780 Timestamp [UCT]: 2024-02-11 14:29:40 Age [y:d:h:m:s]: 00:337:20:53:41
Block: 955257 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241879 RingCT/type: yes/0
Extra: 0149d8a21f92fd8df81c6d89ad8a7718104bdb4953a6cfc3d872a0fbd534624d8102110000000f52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e32d2ca60c96a8af26deea6dfa62be3f90319beac045de8794e3eeff1ab3bf1 0.600000000000 1414543 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": 955267, "vin": [ { "gen": { "height": 955257 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e32d2ca60c96a8af26deea6dfa62be3f90319beac045de8794e3eeff1ab3bf1" } } ], "extra": [ 1, 73, 216, 162, 31, 146, 253, 141, 248, 28, 109, 137, 173, 138, 119, 24, 16, 75, 219, 73, 83, 166, 207, 195, 216, 114, 160, 251, 213, 52, 98, 77, 129, 2, 17, 0, 0, 0, 15, 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