Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c365e9b001a9e66e7aa5790e6fab94141b80b363596b33936b263ad0558c1c4a

Tx prefix hash: 665e748db0841bff842c190d9f0e0346e135e1f34b588ba91ef1d5c20988d9e5
Tx public key: 4e5f3f33c111338365b49f4476b7cb330fc4e749f34aa9b5c60cb8b0b5a31af5
Timestamp: 1698252253 Timestamp [UCT]: 2023-10-25 16:44:13 Age [y:d:h:m:s]: 01:174:03:42:04
Block: 877467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385478 RingCT/type: yes/0
Extra: 014e5f3f33c111338365b49f4476b7cb330fc4e749f34aa9b5c60cb8b0b5a31af502110000000133af99f4000000000000000000

1 output(s) for total of 0.759604610000 dcy

stealth address amount amount idx
00: 6d86c6a137b8dfefa743cbfb4777e4830051e0bde4356cdc567bab1508532b97 0.759604610000 1332843 of 0

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": 877477, "vin": [ { "gen": { "height": 877467 } } ], "vout": [ { "amount": 759604610, "target": { "key": "6d86c6a137b8dfefa743cbfb4777e4830051e0bde4356cdc567bab1508532b97" } } ], "extra": [ 1, 78, 95, 63, 51, 193, 17, 51, 131, 101, 180, 159, 68, 118, 183, 203, 51, 15, 196, 231, 73, 243, 74, 169, 181, 198, 12, 184, 176, 181, 163, 26, 245, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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