Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cd0afbd094cfcc7b96449a8a5642bde6e6aca850a68e62babb7d223a7f46289

Tx prefix hash: a778e12484457dc9b4f17a0d05c1d111fc90308bd77b92378e6ebadf0771f1f3
Tx public key: b11114fd0f8250aa7284651e4c814bbaeca5ae40cb4c554dc26f30d30ec2acef
Timestamp: 1709817778 Timestamp [UCT]: 2024-03-07 13:22:58 Age [y:d:h:m:s]: 01:007:08:45:24
Block: 973159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266247 RingCT/type: yes/0
Extra: 01b11114fd0f8250aa7284651e4c814bbaeca5ae40cb4c554dc26f30d30ec2acef0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bbaf4e4e0700081fa2bf780fc966c9069d19575b00c3b82c098d47788ae5bd6d 0.600000000000 1433092 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": 973169, "vin": [ { "gen": { "height": 973159 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbaf4e4e0700081fa2bf780fc966c9069d19575b00c3b82c098d47788ae5bd6d" } } ], "extra": [ 1, 177, 17, 20, 253, 15, 130, 80, 170, 114, 132, 101, 30, 76, 129, 75, 186, 236, 165, 174, 64, 203, 76, 85, 77, 194, 111, 48, 211, 14, 194, 172, 239, 2, 17, 0, 0, 0, 3, 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