Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4df0476cd87221d0ed49ed9d8014dbf6212ab1a761b6fa651517badfe3e2a204

Tx prefix hash: 13c50add673e16e77daa39afeea757bcae2e50c2729ad5447a8e0643d749dfaa
Tx public key: f40bb7e732e5417fd30dd54d7681a07338c9c056aafe65c82f0714e9f97a761d
Timestamp: 1711547982 Timestamp [UCT]: 2024-03-27 13:59:42 Age [y:d:h:m:s]: 00:293:13:03:46
Block: 987508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210097 RingCT/type: yes/0
Extra: 01f40bb7e732e5417fd30dd54d7681a07338c9c056aafe65c82f0714e9f97a761d0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c5cb00cda759eb47c1ae745a37685cfcd4cda753948f917cebd7f3f1a8737fb 0.600000000000 1447759 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": 987518, "vin": [ { "gen": { "height": 987508 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c5cb00cda759eb47c1ae745a37685cfcd4cda753948f917cebd7f3f1a8737fb" } } ], "extra": [ 1, 244, 11, 183, 231, 50, 229, 65, 127, 211, 13, 213, 77, 118, 129, 160, 115, 56, 201, 192, 86, 170, 254, 101, 200, 47, 7, 20, 233, 249, 122, 118, 29, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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