Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b33ad5dad9a6579ab5c7f66a683db77e6884815fe35f5191cc1bc6821de6ba5a

Tx prefix hash: afd53c01dc0715f8709ad0bbd58f9f9a55927b08f1dc409119dd51de9941224e
Tx public key: f914a14cf5a41bf1c6e9149cad60aaf4e2a34061e1add33952854d87a6640e25
Timestamp: 1583531332 Timestamp [UCT]: 2020-03-06 21:48:52 Age [y:d:h:m:s]: 05:101:15:10:01
Block: 77655 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1227887 RingCT/type: yes/0
Extra: 01f914a14cf5a41bf1c6e9149cad60aaf4e2a34061e1add33952854d87a6640e25021100000001e89b4e54000000000000000000

1 output(s) for total of 339.388828114000 dcy

stealth address amount amount idx
00: 79c2b520b4d843f6ff4d06c899a05769e1a9f4d572a13c217627063bd7844686 339.388828114000 142816 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": 77665, "vin": [ { "gen": { "height": 77655 } } ], "vout": [ { "amount": 339388828114, "target": { "key": "79c2b520b4d843f6ff4d06c899a05769e1a9f4d572a13c217627063bd7844686" } } ], "extra": [ 1, 249, 20, 161, 76, 245, 164, 27, 241, 198, 233, 20, 156, 173, 96, 170, 244, 226, 163, 64, 97, 225, 173, 211, 57, 82, 133, 77, 135, 166, 100, 14, 37, 2, 17, 0, 0, 0, 1, 232, 155, 78, 84, 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