Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d1a31e90dbb41056ae7cc3c50834be0b14d0b31b6238d5e69e441dc3b3fbb32

Tx prefix hash: 77cc4c9d430ba81b10276795f028495ef978ec1c9341012d37a749f0aeedc4e3
Tx public key: 8ce3e6f2bd96019f03dcf1735d868a6b807caeb91a05c97600fd7a64387c1e19
Timestamp: 1720800964 Timestamp [UCT]: 2024-07-12 16:16:04 Age [y:d:h:m:s]: 00:199:03:03:17
Block: 1064206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142225 RingCT/type: yes/0
Extra: 018ce3e6f2bd96019f03dcf1735d868a6b807caeb91a05c97600fd7a64387c1e1902110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50695c684608f3566ab30a4b7aa1c991ed4b44c3945e5e0db0409b38ed1c4e58 0.600000000000 1534729 of 15

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": 1064216, "vin": [ { "gen": { "height": 1064206 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50695c684608f3566ab30a4b7aa1c991ed4b44c3945e5e0db0409b38ed1c4e58" } } ], "extra": [ 1, 140, 227, 230, 242, 189, 150, 1, 159, 3, 220, 241, 115, 93, 134, 138, 107, 128, 124, 174, 185, 26, 5, 201, 118, 0, 253, 122, 100, 56, 124, 30, 25, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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