Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb6c995add7bc5293da19705d91acb0a77c35bce4008d107a007ba48c3935fe1

Tx prefix hash: bcb8d593f43cf090e40f91c069b26acbe0ac5227e82c2dec56e721ca7cfa5806
Tx public key: 8fb9bcaeeb1b94a8c6f1a04a8f185a518d585234aaa67b899ced35c4e0daf472
Timestamp: 1659361451 Timestamp [UCT]: 2022-08-01 13:44:11 Age [y:d:h:m:s]: 02:125:06:10:52
Block: 556422 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 610927 RingCT/type: yes/0
Extra: 018fb9bcaeeb1b94a8c6f1a04a8f185a518d585234aaa67b899ced35c4e0daf472021100000008aac913b7000000000000000000

1 output(s) for total of 8.797171430000 dcy

stealth address amount amount idx
00: 717c4940fde34678706e6c2bf01b6ae1ac6e1bae431cdaf7270f1d3e1ebd8a9e 8.797171430000 988360 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": 556432, "vin": [ { "gen": { "height": 556422 } } ], "vout": [ { "amount": 8797171430, "target": { "key": "717c4940fde34678706e6c2bf01b6ae1ac6e1bae431cdaf7270f1d3e1ebd8a9e" } } ], "extra": [ 1, 143, 185, 188, 174, 235, 27, 148, 168, 198, 241, 160, 74, 143, 24, 90, 81, 141, 88, 82, 52, 170, 166, 123, 137, 156, 237, 53, 196, 224, 218, 244, 114, 2, 17, 0, 0, 0, 8, 170, 201, 19, 183, 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