Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c79b21ed3b9ac3bfccd0c43220894c9dd1afd00597df8db406e55a6dd199833

Tx prefix hash: 0b3eff4425564723bd24d3a851676abd6a11d770ce0dd092c11a7bd520a6070b
Tx public key: cb130a297a0a76ee6fdd15e0b276c697e0e59b4314c22c89767377145e45a415
Timestamp: 1702776984 Timestamp [UCT]: 2023-12-17 01:36:24 Age [y:d:h:m:s]: 01:034:09:59:08
Block: 914765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285916 RingCT/type: yes/0
Extra: 01cb130a297a0a76ee6fdd15e0b276c697e0e59b4314c22c89767377145e45a41502110000000333af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d890ed9e8a2dfe818f75ef99927897c4d0f8b52d4fe41a81c3999c3e3c5c204 0.600000000000 1372117 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": 914775, "vin": [ { "gen": { "height": 914765 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d890ed9e8a2dfe818f75ef99927897c4d0f8b52d4fe41a81c3999c3e3c5c204" } } ], "extra": [ 1, 203, 19, 10, 41, 122, 10, 118, 238, 111, 221, 21, 224, 178, 118, 198, 151, 224, 229, 155, 67, 20, 194, 44, 137, 118, 115, 119, 20, 94, 69, 164, 21, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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