Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e977916b189b4108d24de1fc5cc5d3d49a8643d406cc39a65b04af2a95158f98

Tx prefix hash: 6d646fcf2d5540ef2046af48e61a94e75d383c5e4b34f8a134352797841d1906
Tx public key: 164d8804014547962956a6f0d1149aedc71d5dbaa9c69ad659df0daf29df2f79
Timestamp: 1702557937 Timestamp [UCT]: 2023-12-14 12:45:37 Age [y:d:h:m:s]: 01:327:03:15:58
Block: 912950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492647 RingCT/type: yes/0
Extra: 01164d8804014547962956a6f0d1149aedc71d5dbaa9c69ad659df0daf29df2f7902110000000975e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 033b599c0d71b35f6aaac48ecdc19ee0eca4d42631e3f4394d8df0ad99e71a6c 0.600000000000 1370186 of 15

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": 912960, "vin": [ { "gen": { "height": 912950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "033b599c0d71b35f6aaac48ecdc19ee0eca4d42631e3f4394d8df0ad99e71a6c" } } ], "extra": [ 1, 22, 77, 136, 4, 1, 69, 71, 150, 41, 86, 166, 240, 209, 20, 154, 237, 199, 29, 93, 186, 169, 198, 154, 214, 89, 223, 13, 175, 41, 223, 47, 121, 2, 17, 0, 0, 0, 9, 117, 227, 240, 233, 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