Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c91c0bf5c891baffcb814910e9d5a07d819798d073464f35d2af2edf0057461e

Tx prefix hash: df82ff8fc9c0ff4af064f428485a2f73aa494feb4b783e9729f3d31b3c3236f4
Tx public key: 7256286df8101d249dbb64ee68ef5730697137dacca761d068d0a7638a8fdcaa
Timestamp: 1730310250 Timestamp [UCT]: 2024-10-30 17:44:10 Age [y:d:h:m:s]: 00:112:18:28:57
Block: 1142956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80388 RingCT/type: yes/0
Extra: 017256286df8101d249dbb64ee68ef5730697137dacca761d068d0a7638a8fdcaa0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8d94d3844a5218343e565cba04a6b4d3d29b45eeb9e941a7fb96cb0ad8972f3 0.600000000000 1626813 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": 1142966, "vin": [ { "gen": { "height": 1142956 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8d94d3844a5218343e565cba04a6b4d3d29b45eeb9e941a7fb96cb0ad8972f3" } } ], "extra": [ 1, 114, 86, 40, 109, 248, 16, 29, 36, 157, 187, 100, 238, 104, 239, 87, 48, 105, 113, 55, 218, 204, 167, 97, 208, 104, 208, 167, 99, 138, 143, 220, 170, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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