Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4af3db7644cf72138fe2650608104c57c45988f5e4f0397b1cdd6d2e101409cd

Tx prefix hash: f5179d9cc63e62c505d2897f71235c680b09247c4d846b5f685fd6fe1f9fd7e4
Tx public key: 725b4f4d1c8309f4aec679f7d7fcd427eae9f2e66a5b675f6888c801cc460f66
Timestamp: 1737406955 Timestamp [UCT]: 2025-01-20 21:02:35 Age [y:d:h:m:s]: 00:149:23:45:16
Block: 1201677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106919 RingCT/type: yes/0
Extra: 01725b4f4d1c8309f4aec679f7d7fcd427eae9f2e66a5b675f6888c801cc460f66021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 687c743473cd0e7ba408f9dcb2d2eaccc9f7a20ac5cabb9459a08978b0864168 0.600000000000 1688334 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": 1201687, "vin": [ { "gen": { "height": 1201677 } } ], "vout": [ { "amount": 600000000, "target": { "key": "687c743473cd0e7ba408f9dcb2d2eaccc9f7a20ac5cabb9459a08978b0864168" } } ], "extra": [ 1, 114, 91, 79, 77, 28, 131, 9, 244, 174, 198, 121, 247, 215, 252, 212, 39, 234, 233, 242, 230, 106, 91, 103, 95, 104, 136, 200, 1, 204, 70, 15, 102, 2, 17, 0, 0, 0, 4, 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