Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ad1be02747410c1843d429e72d4a520cc431a34cdc3fd3272b28112540b32fb

Tx prefix hash: 15dbe4868e40231e7c9ac5f9f498fb0d84c527a5ab69f57608cce8f3d8194b9f
Tx public key: 7ba7b75dbf24a88ac0940ddb3e2cc54147419bf89c68cdea297209b75ca0cd52
Timestamp: 1728930298 Timestamp [UCT]: 2024-10-14 18:24:58 Age [y:d:h:m:s]: 00:101:04:09:07
Block: 1131595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72267 RingCT/type: yes/0
Extra: 017ba7b75dbf24a88ac0940ddb3e2cc54147419bf89c68cdea297209b75ca0cd5202110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d045f6497d57411214cc150ef0d2e1a1bb2f398a500d1f7bc6d1e8de0970f188 0.600000000000 1614498 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": 1131605, "vin": [ { "gen": { "height": 1131595 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d045f6497d57411214cc150ef0d2e1a1bb2f398a500d1f7bc6d1e8de0970f188" } } ], "extra": [ 1, 123, 167, 183, 93, 191, 36, 168, 138, 192, 148, 13, 219, 62, 44, 197, 65, 71, 65, 155, 248, 156, 104, 205, 234, 41, 114, 9, 183, 92, 160, 205, 82, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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