Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f36c4eb2de8513ea786ec31726220bfa444e8dd67160ee581f17ff3982c8938b

Tx prefix hash: 48908980dc89a1d49650d05759b1fcb924912f17a2d1b28ca108572cc39c6d95
Tx public key: 53eba3a130a8af978099fb6d79508803a233a3f2c53a935a92799e4cacf4b1cf
Timestamp: 1734985881 Timestamp [UCT]: 2024-12-23 20:31:21 Age [y:d:h:m:s]: 00:091:23:41:10
Block: 1181715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65476 RingCT/type: yes/0
Extra: 0153eba3a130a8af978099fb6d79508803a233a3f2c53a935a92799e4cacf4b1cf02110000000ad4a401e0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10f447a0d4f69a54f04f232ac434f66e0d7f8ed167c8bf6a13d330ee6d198fc0 0.600000000000 1668140 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": 1181725, "vin": [ { "gen": { "height": 1181715 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10f447a0d4f69a54f04f232ac434f66e0d7f8ed167c8bf6a13d330ee6d198fc0" } } ], "extra": [ 1, 83, 235, 163, 161, 48, 168, 175, 151, 128, 153, 251, 109, 121, 80, 136, 3, 162, 51, 163, 242, 197, 58, 147, 90, 146, 121, 158, 76, 172, 244, 177, 207, 2, 17, 0, 0, 0, 10, 212, 164, 1, 224, 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