Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6430e7e499be64337f11688966f024bb8055bf617ec76789936e682a032ebdd9

Tx prefix hash: f3633fdd6710b4740fa6cc72c1b14e6f4de3fca277ae8a3f0b47a4926e6b784c
Tx public key: 64d22b92fc0a662c4eaeb87186a076d0aac5c41244e6cc3d03df5a3238b58210
Timestamp: 1714782942 Timestamp [UCT]: 2024-05-04 00:35:42 Age [y:d:h:m:s]: 00:191:05:31:57
Block: 1014312 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136879 RingCT/type: yes/0
Extra: 0164d22b92fc0a662c4eaeb87186a076d0aac5c41244e6cc3d03df5a3238b5821002110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7186757e52734158065c3483151e14bc1f6feb7bf344b3e7887d96bb4ac3730 0.600000000000 1477363 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": 1014322, "vin": [ { "gen": { "height": 1014312 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7186757e52734158065c3483151e14bc1f6feb7bf344b3e7887d96bb4ac3730" } } ], "extra": [ 1, 100, 210, 43, 146, 252, 10, 102, 44, 78, 174, 184, 113, 134, 160, 118, 208, 170, 197, 196, 18, 68, 230, 204, 61, 3, 223, 90, 50, 56, 181, 130, 16, 2, 17, 0, 0, 0, 2, 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