Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91de9576e9cc13e4b7204089bd497f871159f90ceebf5d064c5891c1236ca7ba

Tx prefix hash: f4e7a7b51936a9aabc062a9dbf234eab9eb843e42553b84438bb6d9f4b350af5
Tx public key: f2bb0a835bec8da04832fff23e94b39eaaebcdcc87f1e55aa4ce1c11157848c8
Timestamp: 1685122739 Timestamp [UCT]: 2023-05-26 17:38:59 Age [y:d:h:m:s]: 01:353:23:13:13
Block: 768656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 514217 RingCT/type: yes/0
Extra: 01f2bb0a835bec8da04832fff23e94b39eaaebcdcc87f1e55aa4ce1c11157848c8021100000001b3164c24000000000000000000

1 output(s) for total of 1.742303317000 dcy

stealth address amount amount idx
00: 618b53dad9875bf45802d52e0e67379892e88d02c2e1932ed34c641573e8a53f 1.742303317000 1217863 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": 768666, "vin": [ { "gen": { "height": 768656 } } ], "vout": [ { "amount": 1742303317, "target": { "key": "618b53dad9875bf45802d52e0e67379892e88d02c2e1932ed34c641573e8a53f" } } ], "extra": [ 1, 242, 187, 10, 131, 91, 236, 141, 160, 72, 50, 255, 242, 62, 148, 179, 158, 170, 235, 205, 204, 135, 241, 229, 90, 164, 206, 28, 17, 21, 120, 72, 200, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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