Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36e18e6aa6a4d9c2467fc6b3eb06b74269b71c830d5a10f0e582155076f86af5

Tx prefix hash: d36a566f7da003791db694cec70cb4bbf6945cd09e13b22b40e9822a3c490d61
Tx public key: 16e40efcb1c9b4eae4d513254fad12cfa430e8b026b90dda7d98e10ee54b3e79
Timestamp: 1735903232 Timestamp [UCT]: 2025-01-03 11:20:32 Age [y:d:h:m:s]: 00:353:02:45:14
Block: 1189291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249905 RingCT/type: yes/0
Extra: 0116e40efcb1c9b4eae4d513254fad12cfa430e8b026b90dda7d98e10ee54b3e7902110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 22146ce1d70a4c4f3ebb7d731c2e3c04004feb4cd0de1a2e2d433ab936743912 0.600000000000 1675798 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": 1189301, "vin": [ { "gen": { "height": 1189291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22146ce1d70a4c4f3ebb7d731c2e3c04004feb4cd0de1a2e2d433ab936743912" } } ], "extra": [ 1, 22, 228, 14, 252, 177, 201, 180, 234, 228, 213, 19, 37, 79, 173, 18, 207, 164, 48, 232, 176, 38, 185, 13, 218, 125, 152, 225, 14, 229, 75, 62, 121, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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