Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd6a38b946023811b5dcfb30998368283168d8927a8b2e65faae89ab4db64f23

Tx prefix hash: 0f18529fdc4688900438b2433ed72de6e7e834f3e1a1f535ab75d2593d0c396c
Tx public key: 31777b7e032ae4d10d492e8d07d3ae816ac5986ffdd0b075e8d0c9ccf7700ba6
Timestamp: 1718529076 Timestamp [UCT]: 2024-06-16 09:11:16 Age [y:d:h:m:s]: 00:333:15:36:30
Block: 1045380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238433 RingCT/type: yes/0
Extra: 0131777b7e032ae4d10d492e8d07d3ae816ac5986ffdd0b075e8d0c9ccf7700ba602110000000136ea7c8b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0d4d5294b221c0bbba8a0ada26e58487bb87caf2de2b09fcea0e2a4bc3e97a7 0.600000000000 1514933 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": 1045390, "vin": [ { "gen": { "height": 1045380 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0d4d5294b221c0bbba8a0ada26e58487bb87caf2de2b09fcea0e2a4bc3e97a7" } } ], "extra": [ 1, 49, 119, 123, 126, 3, 42, 228, 209, 13, 73, 46, 141, 7, 211, 174, 129, 106, 197, 152, 111, 253, 208, 176, 117, 232, 208, 201, 204, 247, 112, 11, 166, 2, 17, 0, 0, 0, 1, 54, 234, 124, 139, 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