Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9366e29f8d81995353abd16e598efa9ffbc79609d14abb9e51960b5ce0e1fb1c

Tx prefix hash: a757317c5b1c038ac2b5981f9db04b2ec28a86d1d4f71c4f804ca0ef0e129a21
Tx public key: dd94dc157c6e3fb1693b0d3d102bea2a0386dcd8afcf244e91e5d2f1e28aa29c
Timestamp: 1704123114 Timestamp [UCT]: 2024-01-01 15:31:54 Age [y:d:h:m:s]: 01:094:16:40:20
Block: 925922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328796 RingCT/type: yes/0
Extra: 01dd94dc157c6e3fb1693b0d3d102bea2a0386dcd8afcf244e91e5d2f1e28aa29c0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e11c560dfd58221fdcd95ccaf935bbd1914b01713beb6c8f8b6ce55aea38fa4 0.600000000000 1383692 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": 925932, "vin": [ { "gen": { "height": 925922 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e11c560dfd58221fdcd95ccaf935bbd1914b01713beb6c8f8b6ce55aea38fa4" } } ], "extra": [ 1, 221, 148, 220, 21, 124, 110, 63, 177, 105, 59, 13, 61, 16, 43, 234, 42, 3, 134, 220, 216, 175, 207, 36, 78, 145, 229, 210, 241, 226, 138, 162, 156, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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