Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 996981ee77d912ccab87f946d92b5efd17b2e544415a201ea3e8772297ed7d42

Tx prefix hash: 4cb11a23b1f1a7c7cd1abb83ef626560e786f50ea90d330d274c7fbbeaa907a6
Tx public key: 4294df69472ed4b6394233dc527ee985d4a45b17bf76c8645c32c36842db6a0e
Timestamp: 1713314537 Timestamp [UCT]: 2024-04-17 00:42:17 Age [y:d:h:m:s]: 01:042:01:56:57
Block: 1002117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291067 RingCT/type: yes/0
Extra: 014294df69472ed4b6394233dc527ee985d4a45b17bf76c8645c32c36842db6a0e02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f222c8aab2b2f87078de8b8465974e0c24e4c5b9a0c14631c10eec15354f83df 0.600000000000 1462633 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": 1002127, "vin": [ { "gen": { "height": 1002117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f222c8aab2b2f87078de8b8465974e0c24e4c5b9a0c14631c10eec15354f83df" } } ], "extra": [ 1, 66, 148, 223, 105, 71, 46, 212, 182, 57, 66, 51, 220, 82, 126, 233, 133, 212, 164, 91, 23, 191, 118, 200, 100, 92, 50, 195, 104, 66, 219, 106, 14, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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