Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed8e4d71ae2a09cb70d46071e8351f24d0836e74768c0f0026e209e31e640210

Tx prefix hash: e20c980fbad4570840692555c75165cfa21a5550471f8fcd07b52d48a4bdb09a
Tx public key: 7a734c01f7ef396dbd36bab446fa3407fdb9ca473e8927efc7c8f8cf99d822c8
Timestamp: 1710323248 Timestamp [UCT]: 2024-03-13 09:47:28 Age [y:d:h:m:s]: 00:347:18:40:59
Block: 977341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248631 RingCT/type: yes/0
Extra: 017a734c01f7ef396dbd36bab446fa3407fdb9ca473e8927efc7c8f8cf99d822c802110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fbbc3c2810ea3fbd20f37736fd9e41da4d6aac22f5a2c4fc5ad1054fab9dec18 0.600000000000 1437344 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": 977351, "vin": [ { "gen": { "height": 977341 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbbc3c2810ea3fbd20f37736fd9e41da4d6aac22f5a2c4fc5ad1054fab9dec18" } } ], "extra": [ 1, 122, 115, 76, 1, 247, 239, 57, 109, 189, 54, 186, 180, 70, 250, 52, 7, 253, 185, 202, 71, 62, 137, 39, 239, 199, 200, 248, 207, 153, 216, 34, 200, 2, 17, 0, 0, 0, 11, 122, 156, 244, 199, 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