Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81510aa60ca07bbf55e3e4d5d53178c3384742b12a383adfef5f11fe7f77a826

Tx prefix hash: e970a61116ae60ee97edd62f4f51b64c6e1162941320bfaff344f06e6139987b
Tx public key: 8f726f63cb91314817e18fef1025fa0c54ba7f0533791cd5e84e9c8a3f1baccb
Timestamp: 1727026869 Timestamp [UCT]: 2024-09-22 17:41:09 Age [y:d:h:m:s]: 00:193:20:42:37
Block: 1115817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138366 RingCT/type: yes/0
Extra: 018f726f63cb91314817e18fef1025fa0c54ba7f0533791cd5e84e9c8a3f1baccb02110000001191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5f30faed17385e3d7789aa4777e7b798c02ce49086c1c8872f4f17639aac7dc 0.600000000000 1596078 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": 1115827, "vin": [ { "gen": { "height": 1115817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5f30faed17385e3d7789aa4777e7b798c02ce49086c1c8872f4f17639aac7dc" } } ], "extra": [ 1, 143, 114, 111, 99, 203, 145, 49, 72, 23, 225, 143, 239, 16, 37, 250, 12, 84, 186, 127, 5, 51, 121, 28, 213, 232, 78, 156, 138, 63, 27, 172, 203, 2, 17, 0, 0, 0, 17, 145, 225, 60, 4, 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