Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edda328772c54e4fa67a602a5efb37cd29dece32495cd5048f589929baf8f13a

Tx prefix hash: 376d7ae0f95beef4efca38d980d56e283e9a6c5b584cad85d718f9a521b43788
Tx public key: fb591991210bf4e05c75441098621f7578a2f8ca6f7ff4ca88378b61b5deedd2
Timestamp: 1699877023 Timestamp [UCT]: 2023-11-13 12:03:43 Age [y:d:h:m:s]: 01:002:16:23:34
Block: 890729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263271 RingCT/type: yes/0
Extra: 01fb591991210bf4e05c75441098621f7578a2f8ca6f7ff4ca88378b61b5deedd2021100000007faf35c9c000000000000000000

1 output(s) for total of 0.686517144000 dcy

stealth address amount amount idx
00: 066314f5ddcd0a20bd62ca0cf4de2a0e7d54d77e06fff7e24c19101aaef4f463 0.686517144000 1346758 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": 890739, "vin": [ { "gen": { "height": 890729 } } ], "vout": [ { "amount": 686517144, "target": { "key": "066314f5ddcd0a20bd62ca0cf4de2a0e7d54d77e06fff7e24c19101aaef4f463" } } ], "extra": [ 1, 251, 89, 25, 145, 33, 11, 244, 224, 92, 117, 68, 16, 152, 98, 31, 117, 120, 162, 248, 202, 111, 127, 244, 202, 136, 55, 139, 97, 181, 222, 237, 210, 2, 17, 0, 0, 0, 7, 250, 243, 92, 156, 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