Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a68d3e85a8ea2838f43d5a3545bb44cac6d260578d859a74e9f4916315d6b1c4

Tx prefix hash: 651f36dc91efc876396b1eb070975193304407496f0f5f8c4ae8721a7bc453de
Tx public key: 43e20957b3e6d9d10e70bd529f166883954f4472c208551cd18a3bd453b42b07
Timestamp: 1677928712 Timestamp [UCT]: 2023-03-04 11:18:32 Age [y:d:h:m:s]: 02:041:01:14:42
Block: 709647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 550919 RingCT/type: yes/0
Extra: 0143e20957b3e6d9d10e70bd529f166883954f4472c208551cd18a3bd453b42b07021100000003835e4d22000000000000000000

1 output(s) for total of 2.733032522000 dcy

stealth address amount amount idx
00: 178efcce1cf0b4e4c92d264f67d0a539b44b3c412077629282653fba29be8dbf 2.733032522000 1153656 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": 709657, "vin": [ { "gen": { "height": 709647 } } ], "vout": [ { "amount": 2733032522, "target": { "key": "178efcce1cf0b4e4c92d264f67d0a539b44b3c412077629282653fba29be8dbf" } } ], "extra": [ 1, 67, 226, 9, 87, 179, 230, 217, 209, 14, 112, 189, 82, 159, 22, 104, 131, 149, 79, 68, 114, 194, 8, 85, 28, 209, 138, 59, 212, 83, 180, 43, 7, 2, 17, 0, 0, 0, 3, 131, 94, 77, 34, 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