Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fbe8aec29c0ecbdbc8c4133e40219ea3435d13d5f9602fd0f45594c861bd3db

Tx prefix hash: 007a13657b5154852d9322aae4c2128c1dc3f330311f84506e813aa6fa18a830
Tx public key: 4514cbfe2ae4ae08c483b3aacb0fbe4462364baead9feb206ef134682251a909
Timestamp: 1719032565 Timestamp [UCT]: 2024-06-22 05:02:45 Age [y:d:h:m:s]: 00:273:04:11:12
Block: 1049522 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195217 RingCT/type: yes/0
Extra: 014514cbfe2ae4ae08c483b3aacb0fbe4462364baead9feb206ef134682251a9090211000000015ff1157f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9039313f164ca313227f2fe781affee87cf1d66c75d3bd913edb0f6f4d72124 0.600000000000 1519621 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": 1049532, "vin": [ { "gen": { "height": 1049522 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9039313f164ca313227f2fe781affee87cf1d66c75d3bd913edb0f6f4d72124" } } ], "extra": [ 1, 69, 20, 203, 254, 42, 228, 174, 8, 196, 131, 179, 170, 203, 15, 190, 68, 98, 54, 75, 174, 173, 159, 235, 32, 110, 241, 52, 104, 34, 81, 169, 9, 2, 17, 0, 0, 0, 1, 95, 241, 21, 127, 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