Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d19886ec46da4d4bf197aeaeb6969ff80fab1bb6da512204adeddd2d0db7e6a

Tx prefix hash: d7050b80a416810fb61f57fe564b3311453c516a5309872bc0c2ededc7ebdf71
Tx public key: f3de1c42bc71722482217974fd5b48a1cf11a9e859e87eaf6b4f3e16f68f29d4
Timestamp: 1694266347 Timestamp [UCT]: 2023-09-09 13:32:27 Age [y:d:h:m:s]: 01:213:19:43:15
Block: 844391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413925 RingCT/type: yes/0
Extra: 01f3de1c42bc71722482217974fd5b48a1cf11a9e859e87eaf6b4f3e16f68f29d40211000000074b8f5122000000000000000000

1 output(s) for total of 0.977647195000 dcy

stealth address amount amount idx
00: f5cddc7c23cd2aa0c71bcb90ebd783ca3e3b6f9dc5a72366914a0b16da12393c 0.977647195000 1297697 of 0

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": 844401, "vin": [ { "gen": { "height": 844391 } } ], "vout": [ { "amount": 977647195, "target": { "key": "f5cddc7c23cd2aa0c71bcb90ebd783ca3e3b6f9dc5a72366914a0b16da12393c" } } ], "extra": [ 1, 243, 222, 28, 66, 188, 113, 114, 36, 130, 33, 121, 116, 253, 91, 72, 161, 207, 17, 169, 232, 89, 232, 126, 175, 107, 79, 62, 22, 246, 143, 41, 212, 2, 17, 0, 0, 0, 7, 75, 143, 81, 34, 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