Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2739b214b4a0c1ea3bf4a4095e6065cc0cfc4ba717fdb461bd1c946199733b2d

Tx prefix hash: bb1bd83865a894dbf9d7939059333e1f978e3446fcf6dae265f0db1835a8ba57
Tx public key: d17ffc5e127fed2ffc220067b960c682ac05141762f18217bdc7c26ff659ffc6
Timestamp: 1700825054 Timestamp [UCT]: 2023-11-24 11:24:14 Age [y:d:h:m:s]: 01:171:09:42:53
Block: 898579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383705 RingCT/type: yes/0
Extra: 01d17ffc5e127fed2ffc220067b960c682ac05141762f18217bdc7c26ff659ffc6021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.646598571000 dcy

stealth address amount amount idx
00: f41a88dbb88a769d0d28065be8d0df7aaf5e1bdbf347fc31c5785aa2c8f8c280 0.646598571000 1355000 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": 898589, "vin": [ { "gen": { "height": 898579 } } ], "vout": [ { "amount": 646598571, "target": { "key": "f41a88dbb88a769d0d28065be8d0df7aaf5e1bdbf347fc31c5785aa2c8f8c280" } } ], "extra": [ 1, 209, 127, 252, 94, 18, 127, 237, 47, 252, 34, 0, 103, 185, 96, 198, 130, 172, 5, 20, 23, 98, 241, 130, 23, 189, 199, 194, 111, 246, 89, 255, 198, 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