Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cbb2772647408d7b8190e91e015f0546c60d3babc0d1cea21288329045d7a17

Tx prefix hash: 80d9ba9cf9ee095d062b39af31c638f1a37f3cfad50ea91522a4886397765306
Tx public key: bf3b63afc1bb6a2613a567672fb27b95ee40fa4d1e716c50a703c056c04e1100
Timestamp: 1732290394 Timestamp [UCT]: 2024-11-22 15:46:34 Age [y:d:h:m:s]: 00:001:14:12:11
Block: 1159350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1140 RingCT/type: yes/0
Extra: 01bf3b63afc1bb6a2613a567672fb27b95ee40fa4d1e716c50a703c056c04e11000211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3bcf27d14cba32d3bf560e4d0fe6b0e46c9a30fca3e6ee3db6ecd2c47901ef05 0.600000000000 1644983 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": 1159360, "vin": [ { "gen": { "height": 1159350 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bcf27d14cba32d3bf560e4d0fe6b0e46c9a30fca3e6ee3db6ecd2c47901ef05" } } ], "extra": [ 1, 191, 59, 99, 175, 193, 187, 106, 38, 19, 165, 103, 103, 47, 178, 123, 149, 238, 64, 250, 77, 30, 113, 108, 80, 167, 3, 192, 86, 192, 78, 17, 0, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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