Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b600f741f662fa443936ccf69244eda463ef08390848bc24591c0041dea5285f

Tx prefix hash: 24d07e26f3b456cc052b13c581f7a2b88563409b39ebb67408ff3b5da68d4204
Tx public key: 78644098218dc419a1f2f0948bdd8dac0b30169f4741e5a1a0706b2f861b0a45
Timestamp: 1710576278 Timestamp [UCT]: 2024-03-16 08:04:38 Age [y:d:h:m:s]: 01:009:20:14:59
Block: 979446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267981 RingCT/type: yes/0
Extra: 0178644098218dc419a1f2f0948bdd8dac0b30169f4741e5a1a0706b2f861b0a450211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b135c58570f20738cfd85e1ab8f6732a6381ef6f9b12b19b53c1ee2287a034c 0.600000000000 1439479 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": 979456, "vin": [ { "gen": { "height": 979446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b135c58570f20738cfd85e1ab8f6732a6381ef6f9b12b19b53c1ee2287a034c" } } ], "extra": [ 1, 120, 100, 64, 152, 33, 141, 196, 25, 161, 242, 240, 148, 139, 221, 141, 172, 11, 48, 22, 159, 71, 65, 229, 161, 160, 112, 107, 47, 134, 27, 10, 69, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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