Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0094b9ff1c2ab69e99f01b522cc3ceab51f028da42ecf2e3a9ed974399f81901

Tx prefix hash: 31a3d53e5ec3671e744e4ad457a11cc74f136b5ad55e53984a679a3cfd1e60a9
Tx public key: 2692a9d429f205a0565a9e88d49755b32f7ee5d6132855e2433e9b03a06dfd97
Timestamp: 1706304232 Timestamp [UCT]: 2024-01-26 21:23:52 Age [y:d:h:m:s]: 01:082:00:40:03
Block: 943979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319717 RingCT/type: yes/0
Extra: 012692a9d429f205a0565a9e88d49755b32f7ee5d6132855e2433e9b03a06dfd970211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06c4856ec8c50522abac097b3707003f7607b31e29d6ea400d67a3bc6028e66d 0.600000000000 1402205 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": 943989, "vin": [ { "gen": { "height": 943979 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06c4856ec8c50522abac097b3707003f7607b31e29d6ea400d67a3bc6028e66d" } } ], "extra": [ 1, 38, 146, 169, 212, 41, 242, 5, 160, 86, 90, 158, 136, 212, 151, 85, 179, 47, 126, 229, 214, 19, 40, 85, 226, 67, 62, 155, 3, 160, 109, 253, 151, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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