Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2de97d01d0fb261f60c7f8466b17210588ae9640660a8b6e5e8eb7ecccf8dd6

Tx prefix hash: 2dba524d43f3842e3b75587d2d69ab29354c2e8b20b77282a5b22b10ac23ccd6
Tx public key: f7c7288cbb1a58bf2f8b794a336365538f191998074754c495071c48cfd38ffd
Timestamp: 1710387971 Timestamp [UCT]: 2024-03-14 03:46:11 Age [y:d:h:m:s]: 01:016:20:52:07
Block: 977888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273020 RingCT/type: yes/0
Extra: 01f7c7288cbb1a58bf2f8b794a336365538f191998074754c495071c48cfd38ffd0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8cfea7f726fe4c73ca0aa1bb9b23ec234425394bd21b098fe7a3fdc04cc47ed3 0.600000000000 1437895 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": 977898, "vin": [ { "gen": { "height": 977888 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8cfea7f726fe4c73ca0aa1bb9b23ec234425394bd21b098fe7a3fdc04cc47ed3" } } ], "extra": [ 1, 247, 199, 40, 140, 187, 26, 88, 191, 47, 139, 121, 74, 51, 99, 101, 83, 143, 25, 25, 152, 7, 71, 84, 196, 149, 7, 28, 72, 207, 211, 143, 253, 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