Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd7d17c30cc2ca482898509261b64cfd3273ebc1b7e566f9c26ed438a7b825e1

Tx prefix hash: e9cb2f9d0e6be58a0c23dc5ff05894f8f3309a6cac6d638340dd2d6e927cd8c4
Tx public key: 97d43c915fe5f376bcd70aa4032a7c52b9bff0793f40087ef7df1d39dc487fdb
Timestamp: 1582508308 Timestamp [UCT]: 2020-02-24 01:38:28 Age [y:d:h:m:s]: 05:009:23:33:51
Block: 71097 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1160509 RingCT/type: yes/0
Extra: 0197d43c915fe5f376bcd70aa4032a7c52b9bff0793f40087ef7df1d39dc487fdb021100000008d81c26c0000000000000000000

1 output(s) for total of 356.801710168000 dcy

stealth address amount amount idx
00: 96adb440446624417e68e8df979d3e47d210247ae72050e33a71e4487dd4d2fc 356.801710168000 131407 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": 71107, "vin": [ { "gen": { "height": 71097 } } ], "vout": [ { "amount": 356801710168, "target": { "key": "96adb440446624417e68e8df979d3e47d210247ae72050e33a71e4487dd4d2fc" } } ], "extra": [ 1, 151, 212, 60, 145, 95, 229, 243, 118, 188, 215, 10, 164, 3, 42, 124, 82, 185, 191, 240, 121, 63, 64, 8, 126, 247, 223, 29, 57, 220, 72, 127, 219, 2, 17, 0, 0, 0, 8, 216, 28, 38, 192, 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