Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f2b7ee975d85fc9abdb334212f39fd3030cc3f1b35621f05a1e09a8a68a2189

Tx prefix hash: 0f94b750703b9cc95b5c22f60fb47e94c3e95f43f7767c25be6cb888b49696a8
Tx public key: 904bf06294849861c280e2d0dfd2f1cb3100ed7636c64ba5a7b8e5431b92319d
Timestamp: 1693333288 Timestamp [UCT]: 2023-08-29 18:21:28 Age [y:d:h:m:s]: 01:180:16:12:30
Block: 836656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390220 RingCT/type: yes/0
Extra: 01904bf06294849861c280e2d0dfd2f1cb3100ed7636c64ba5a7b8e5431b92319d02110000000675e3f0e9000000000000000000

1 output(s) for total of 1.037078034000 dcy

stealth address amount amount idx
00: 307400e4864af6d5a3fd647e75a7e83765f420b51ca89782f96e056a7ecc2a40 1.037078034000 1289248 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": 836666, "vin": [ { "gen": { "height": 836656 } } ], "vout": [ { "amount": 1037078034, "target": { "key": "307400e4864af6d5a3fd647e75a7e83765f420b51ca89782f96e056a7ecc2a40" } } ], "extra": [ 1, 144, 75, 240, 98, 148, 132, 152, 97, 194, 128, 226, 208, 223, 210, 241, 203, 49, 0, 237, 118, 54, 198, 75, 165, 167, 184, 229, 67, 27, 146, 49, 157, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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