Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f94239c80fad374e3878e5c437834ca63c1ad2da17f8cfc637f3ef9c1bcee0bc

Tx prefix hash: 4dd58bed660b103429172dfa73b7efcd1ed57136a52ed6ebde06a9359dd4e9aa
Tx public key: 4a908c9dd3b193c873aac58768bdd5dd05b6ae0a46c672173e0c3e2ce848dccd
Timestamp: 1722240884 Timestamp [UCT]: 2024-07-29 08:14:44 Age [y:d:h:m:s]: 00:238:00:05:13
Block: 1076133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169997 RingCT/type: yes/0
Extra: 014a908c9dd3b193c873aac58768bdd5dd05b6ae0a46c672173e0c3e2ce848dccd02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7080da7a0cf88e317861d277d95e6b967fcc0fe19712c77f3b203b7ce116909 0.600000000000 1548668 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": 1076143, "vin": [ { "gen": { "height": 1076133 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7080da7a0cf88e317861d277d95e6b967fcc0fe19712c77f3b203b7ce116909" } } ], "extra": [ 1, 74, 144, 140, 157, 211, 177, 147, 200, 115, 170, 197, 135, 104, 189, 213, 221, 5, 182, 174, 10, 70, 198, 114, 23, 62, 12, 62, 44, 232, 72, 220, 205, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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