Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 087ba1533b3d3d4c11f560d1174a05b034f57a684c65a4995c6634c31f99aa23

Tx prefix hash: 771466cd32b6e8777ce1a04c086bdeb3af4830ea37559e8346e0892d636deb58
Tx public key: 7b42c934f855eeecd8c4ae40e5971754b57399c36e05e56b08df17780862a19d
Timestamp: 1598187442 Timestamp [UCT]: 2020-08-23 12:57:22 Age [y:d:h:m:s]: 04:158:06:44:10
Block: 129166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1077270 RingCT/type: yes/0
Extra: 017b42c934f855eeecd8c4ae40e5971754b57399c36e05e56b08df17780862a19d0211000000158a2ee0d9000000000000000000

1 output(s) for total of 229.097390581000 dcy

stealth address amount amount idx
00: 262c9b8152542705b207f2f14e76dabfacc705d5d8dcf79953949ccbaf4de10e 229.097390581000 216696 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": 129176, "vin": [ { "gen": { "height": 129166 } } ], "vout": [ { "amount": 229097390581, "target": { "key": "262c9b8152542705b207f2f14e76dabfacc705d5d8dcf79953949ccbaf4de10e" } } ], "extra": [ 1, 123, 66, 201, 52, 248, 85, 238, 236, 216, 196, 174, 64, 229, 151, 23, 84, 181, 115, 153, 195, 110, 5, 229, 107, 8, 223, 23, 120, 8, 98, 161, 157, 2, 17, 0, 0, 0, 21, 138, 46, 224, 217, 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