Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31b3d376e1d9aa8ce12e66533e7b364117207be3ff6225f8f625571daf1c594e

Tx prefix hash: 9ad78ea6858953c1180249bd2f3a2aeb9a4e5d184ad2f807ea143dc46a302e7d
Tx public key: 466c1496011ff891cdfec02739a8c638c4e101722bf05cb107f39ab3ff2929b0
Timestamp: 1698086370 Timestamp [UCT]: 2023-10-23 18:39:30 Age [y:d:h:m:s]: 01:186:00:38:14
Block: 876085 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393988 RingCT/type: yes/0
Extra: 01466c1496011ff891cdfec02739a8c638c4e101722bf05cb107f39ab3ff2929b0021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.767656149000 dcy

stealth address amount amount idx
00: 8198ccbd50c85f529e855045b6a6a2eee6da13773c4805a08ad5e9aee6d71acc 0.767656149000 1331395 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": 876095, "vin": [ { "gen": { "height": 876085 } } ], "vout": [ { "amount": 767656149, "target": { "key": "8198ccbd50c85f529e855045b6a6a2eee6da13773c4805a08ad5e9aee6d71acc" } } ], "extra": [ 1, 70, 108, 20, 150, 1, 31, 248, 145, 205, 254, 192, 39, 57, 168, 198, 56, 196, 225, 1, 114, 43, 240, 92, 177, 7, 243, 154, 179, 255, 41, 41, 176, 2, 17, 0, 0, 0, 2, 230, 210, 127, 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