Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0860b9ebc324153330a6dfc2dbc328bf16b0e219d69df8bb6e1b399bac7fba9a

Tx prefix hash: a3b3d2b8067f11cde8ba480c5d7b94ff65fc5280d69f9940fda686c900aa3ea5
Tx public key: a67ec7b773ac5652dc6bebe498f7fc4553768841bdf4c450ffb33a91cc3293ba
Timestamp: 1577682493 Timestamp [UCT]: 2019-12-30 05:08:13 Age [y:d:h:m:s]: 04:312:14:34:17
Block: 34796 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1112503 RingCT/type: yes/0
Extra: 01a67ec7b773ac5652dc6bebe498f7fc4553768841bdf4c450ffb33a91cc3293ba02110000000d4943cd9f000000000000000000

1 output(s) for total of 470.692069958000 dcy

stealth address amount amount idx
00: 4521070089deea19ef65befa5ae33a7104ea7dd0fdefb67eb4f1c69ce0608005 470.692069958000 58603 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": 34806, "vin": [ { "gen": { "height": 34796 } } ], "vout": [ { "amount": 470692069958, "target": { "key": "4521070089deea19ef65befa5ae33a7104ea7dd0fdefb67eb4f1c69ce0608005" } } ], "extra": [ 1, 166, 126, 199, 183, 115, 172, 86, 82, 220, 107, 235, 228, 152, 247, 252, 69, 83, 118, 136, 65, 189, 244, 196, 80, 255, 179, 58, 145, 204, 50, 147, 186, 2, 17, 0, 0, 0, 13, 73, 67, 205, 159, 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