Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f4983f0883f45d8ece1101ca9f5a1533e5e7205ab1cd4c2e8ee822361eb5c2d

Tx prefix hash: 3b41c58e17fd6cff5747b0f9984ac59144459ce5a498abab510c7510eb6e2d3e
Tx public key: 3a34ba847f04db21161ff85a921da691e8f2691bd750482b4fa05e548a3a0647
Timestamp: 1728163397 Timestamp [UCT]: 2024-10-05 21:23:17 Age [y:d:h:m:s]: 01:034:14:14:59
Block: 1125238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283103 RingCT/type: yes/0
Extra: 013a34ba847f04db21161ff85a921da691e8f2691bd750482b4fa05e548a3a064702110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86049c54eb71fadcc69fa9c0712c7bf4e2702b01295fdce3fdba48287251e9f7 0.600000000000 1607915 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": 1125248, "vin": [ { "gen": { "height": 1125238 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86049c54eb71fadcc69fa9c0712c7bf4e2702b01295fdce3fdba48287251e9f7" } } ], "extra": [ 1, 58, 52, 186, 132, 127, 4, 219, 33, 22, 31, 248, 90, 146, 29, 166, 145, 232, 242, 105, 27, 215, 80, 72, 43, 79, 160, 94, 84, 138, 58, 6, 71, 2, 17, 0, 0, 0, 6, 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