Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b11ac0100e0deee159ad7f8743bdc68a3d02902537547cb71fff6bc4f3a6b4c2

Tx prefix hash: d70d88f19394b4aa3d82511dc7f3c92bd1eb0e308ef2be04028ce190e8a6a7f7
Tx public key: 3767d148323d4dfcc6311238146a54511d8c3d280be4c000204883c227504c1f
Timestamp: 1740548209 Timestamp [UCT]: 2025-02-26 05:36:49 Age [y:d:h:m:s]: 00:014:11:46:18
Block: 1227442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10391 RingCT/type: yes/0
Extra: 013767d148323d4dfcc6311238146a54511d8c3d280be4c000204883c227504c1f021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25a3e5821e11ebcd544906b20ce63bd3b0dfea1ac44765cfd9d60984f6fbb810 0.600000000000 1714315 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": 1227452, "vin": [ { "gen": { "height": 1227442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25a3e5821e11ebcd544906b20ce63bd3b0dfea1ac44765cfd9d60984f6fbb810" } } ], "extra": [ 1, 55, 103, 209, 72, 50, 61, 77, 252, 198, 49, 18, 56, 20, 106, 84, 81, 29, 140, 61, 40, 11, 228, 192, 0, 32, 72, 131, 194, 39, 80, 76, 31, 2, 17, 0, 0, 0, 2, 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