Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b81a8bec53f7005a5c9c4344ca5cea32052c1babd9ad5be1cb4fa28117acdc87

Tx prefix hash: e4943443e8857757557b8c289e4a4fd2a6f3b47d099a79257ddeb21958509a0b
Tx public key: bdf2824e1a1af832e71b9cc8a7d4cac9afedf5c4dd28a71c70e2f1d01667ceba
Timestamp: 1734611110 Timestamp [UCT]: 2024-12-19 12:25:10 Age [y:d:h:m:s]: 00:100:19:41:28
Block: 1178599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71812 RingCT/type: yes/0
Extra: 01bdf2824e1a1af832e71b9cc8a7d4cac9afedf5c4dd28a71c70e2f1d01667ceba021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e01e8fe67fff0c12ade3877c8693daa6ef23d2d011d01267a2f57c518b437c6d 0.600000000000 1664988 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": 1178609, "vin": [ { "gen": { "height": 1178599 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e01e8fe67fff0c12ade3877c8693daa6ef23d2d011d01267a2f57c518b437c6d" } } ], "extra": [ 1, 189, 242, 130, 78, 26, 26, 248, 50, 231, 27, 156, 200, 167, 212, 202, 201, 175, 237, 245, 196, 221, 40, 167, 28, 112, 226, 241, 208, 22, 103, 206, 186, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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