Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86788dae73fcf0f3e665d7e50b1bc8f0fad107bb595196c8ae6445f949479760

Tx prefix hash: 771a057ed2abca80813fe80725e03ca6a936b770d07a01d1f24e596dad392348
Tx public key: de8a714315bf9e99dcf87fbcd19b56cae24df2479afc158900c0e81d3f89489e
Timestamp: 1698537706 Timestamp [UCT]: 2023-10-29 00:01:46 Age [y:d:h:m:s]: 01:117:16:59:10
Block: 879839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345077 RingCT/type: yes/0
Extra: 01de8a714315bf9e99dcf87fbcd19b56cae24df2479afc158900c0e81d3f89489e02110000000633af99f4000000000000000000

1 output(s) for total of 0.745981689000 dcy

stealth address amount amount idx
00: 25ec1e42b3a2c9539fc6afc1b2e66e1e6c6cb9be36fc4ada0044acde37fd10f8 0.745981689000 1335379 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": 879849, "vin": [ { "gen": { "height": 879839 } } ], "vout": [ { "amount": 745981689, "target": { "key": "25ec1e42b3a2c9539fc6afc1b2e66e1e6c6cb9be36fc4ada0044acde37fd10f8" } } ], "extra": [ 1, 222, 138, 113, 67, 21, 191, 158, 153, 220, 248, 127, 188, 209, 155, 86, 202, 226, 77, 242, 71, 154, 252, 21, 137, 0, 192, 232, 29, 63, 137, 72, 158, 2, 17, 0, 0, 0, 6, 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