Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fcdc5172e808d89997a2358fadb1967c4fa0d2f914456a5c452454e3845c668

Tx prefix hash: 3bedd127a14a81599a770964e5c2e6fc43a6c8a1d3b98a1f55dcd2ebe9d19602
Tx public key: 7b16f8e1a145b483f7334cd8229f88e287d232859f6d3f2e313b72eaff1492e3
Timestamp: 1737650896 Timestamp [UCT]: 2025-01-23 16:48:16 Age [y:d:h:m:s]: 00:147:13:34:55
Block: 1203695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105185 RingCT/type: yes/0
Extra: 017b16f8e1a145b483f7334cd8229f88e287d232859f6d3f2e313b72eaff1492e3021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26379235e9afc15cc9d39d84dae5c06dbe0599dae76f79d0beab512f75c85805 0.600000000000 1690374 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": 1203705, "vin": [ { "gen": { "height": 1203695 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26379235e9afc15cc9d39d84dae5c06dbe0599dae76f79d0beab512f75c85805" } } ], "extra": [ 1, 123, 22, 248, 225, 161, 69, 180, 131, 247, 51, 76, 216, 34, 159, 136, 226, 135, 210, 50, 133, 159, 109, 63, 46, 49, 59, 114, 234, 255, 20, 146, 227, 2, 17, 0, 0, 0, 3, 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