Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbd1e69aef1693c133a73421f8d713f3299a80e79457c0f21942710513a65d9b

Tx prefix hash: 95a47c595dd32b029ae6308d192d0eed5578702e3c031cb50fbaf240abc617dd
Tx public key: 12193e4190473536c2053bdb22724f942cc85e486ebeec7080bb2e34f27af8c1
Timestamp: 1663866760 Timestamp [UCT]: 2022-09-22 17:12:40 Age [y:d:h:m:s]: 02:178:18:19:02
Block: 593508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 649164 RingCT/type: yes/0
Extra: 0112193e4190473536c2053bdb22724f942cc85e486ebeec7080bb2e34f27af8c1021100000001faf35c9c000000000000000000

1 output(s) for total of 6.629208651000 dcy

stealth address amount amount idx
00: 482f11074bf5f2e8f42c9eb1cdc1253fefcd7f9a3a892f0d13ac3a8ebd3763a6 6.629208651000 1028303 of 0

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": 593518, "vin": [ { "gen": { "height": 593508 } } ], "vout": [ { "amount": 6629208651, "target": { "key": "482f11074bf5f2e8f42c9eb1cdc1253fefcd7f9a3a892f0d13ac3a8ebd3763a6" } } ], "extra": [ 1, 18, 25, 62, 65, 144, 71, 53, 54, 194, 5, 59, 219, 34, 114, 79, 148, 44, 200, 94, 72, 110, 190, 236, 112, 128, 187, 46, 52, 242, 122, 248, 193, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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