Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f49ef2fea36dfff480f095bd1fab5b3d25a5d49085d8cba3874ff6ae495222e

Tx prefix hash: 326e26724f9306d22b39cf8de64e7a82e858e01f0b99cdba405c9d90de4fbc49
Tx public key: 174ad161e882a5480992f842810400e22e8ff9b4737a958115bc62beba4d3a16
Timestamp: 1694615182 Timestamp [UCT]: 2023-09-13 14:26:22 Age [y:d:h:m:s]: 02:052:14:03:03
Block: 847283 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 557267 RingCT/type: yes/0
Extra: 01174ad161e882a5480992f842810400e22e8ff9b4737a958115bc62beba4d3a16021100000001faf35c9c000000000000000000

1 output(s) for total of 0.956312335000 dcy

stealth address amount amount idx
00: cbcd8b64dffd5ea4c2072ccd777ff29d1a5616d783888a3f7ff3c354b89c329b 0.956312335000 1300797 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": 847293, "vin": [ { "gen": { "height": 847283 } } ], "vout": [ { "amount": 956312335, "target": { "key": "cbcd8b64dffd5ea4c2072ccd777ff29d1a5616d783888a3f7ff3c354b89c329b" } } ], "extra": [ 1, 23, 74, 209, 97, 232, 130, 165, 72, 9, 146, 248, 66, 129, 4, 0, 226, 46, 143, 249, 180, 115, 122, 149, 129, 21, 188, 98, 190, 186, 77, 58, 22, 2, 17, 0, 0, 0, 1, 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