Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1d4ee8dbf498d9b7394aed5a36eaf64b82c7e11c337ee0bfb62780a1be6d28c

Tx prefix hash: 0beae8789372996cc83769429ab80ca7613f65573f57d1dbfd4c2f500802e419
Tx public key: 6f554a57a3ad49a1f5334fe48e90cf15431cfc7af7781c2509c3521d7e1932f3
Timestamp: 1702703828 Timestamp [UCT]: 2023-12-16 05:17:08 Age [y:d:h:m:s]: 01:035:06:12:08
Block: 914162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286518 RingCT/type: yes/0
Extra: 016f554a57a3ad49a1f5334fe48e90cf15431cfc7af7781c2509c3521d7e1932f302110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33350f39aa08ffe5677bc7c89d331e86b09a3aff357ee7ebd2fbdbaeaaac7ae7 0.600000000000 1371448 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": 914172, "vin": [ { "gen": { "height": 914162 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33350f39aa08ffe5677bc7c89d331e86b09a3aff357ee7ebd2fbdbaeaaac7ae7" } } ], "extra": [ 1, 111, 85, 74, 87, 163, 173, 73, 161, 245, 51, 79, 228, 142, 144, 207, 21, 67, 28, 252, 122, 247, 120, 28, 37, 9, 195, 82, 29, 126, 25, 50, 243, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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