Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b1d81a5b74f0567aca49d4472d2fc507ef7393134e5594d7d572ca2cd66611e

Tx prefix hash: 7450b60e0326021191b77d48f3ca676a977a265f1e67c18278e6948f3456b7c0
Tx public key: a3d7195c4cd5c4edd56f48004216c1c89e419ac2620835d1d28c60d5f8bc444c
Timestamp: 1722550018 Timestamp [UCT]: 2024-08-01 22:06:58 Age [y:d:h:m:s]: 00:243:21:48:16
Block: 1078693 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174212 RingCT/type: yes/0
Extra: 01a3d7195c4cd5c4edd56f48004216c1c89e419ac2620835d1d28c60d5f8bc444c02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfdd96e9d78a02c1651e917c4da38a9c7fbbe305b33cc1f66a13005d6dc5c8cd 0.600000000000 1551332 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": 1078703, "vin": [ { "gen": { "height": 1078693 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfdd96e9d78a02c1651e917c4da38a9c7fbbe305b33cc1f66a13005d6dc5c8cd" } } ], "extra": [ 1, 163, 215, 25, 92, 76, 213, 196, 237, 213, 111, 72, 0, 66, 22, 193, 200, 158, 65, 154, 194, 98, 8, 53, 209, 210, 140, 96, 213, 248, 188, 68, 76, 2, 17, 0, 0, 0, 5, 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