Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ff27809762028b399cef9b236fdf95f2570fd2e1fb77c952253c98ef9b1126f

Tx prefix hash: b1acb94f6eb99f251ac55e39fd31cd79ede6cbbc8af6ef3c31f7e312cbb72ecd
Tx public key: ab8225526f1a56e5cf59395eeb12691328bb329f9506d5f1a62d9c2974344b38
Timestamp: 1707909000 Timestamp [UCT]: 2024-02-14 11:10:00 Age [y:d:h:m:s]: 01:049:14:32:59
Block: 957310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296484 RingCT/type: yes/0
Extra: 01ab8225526f1a56e5cf59395eeb12691328bb329f9506d5f1a62d9c2974344b380211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9606aa056da16117f469f59e2c58932bf988ed157f4120c0c266a774418b5dc 0.600000000000 1416626 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": 957320, "vin": [ { "gen": { "height": 957310 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9606aa056da16117f469f59e2c58932bf988ed157f4120c0c266a774418b5dc" } } ], "extra": [ 1, 171, 130, 37, 82, 111, 26, 86, 229, 207, 89, 57, 94, 235, 18, 105, 19, 40, 187, 50, 159, 149, 6, 213, 241, 166, 45, 156, 41, 116, 52, 75, 56, 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