Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1dcfc47dce674f6d8f7411a0c94fb80fabdb24b250689131e877e8ab3b803ea8

Tx prefix hash: 53bcfa2d104b61441000b044f6b01fd7bb78f0a483cc908dd08194d1b507f414
Tx public key: bb1fa71c6555ca930b5f532e4b689b43a5ef2e6eba1b69ca136f49fe3dbf614b
Timestamp: 1711424687 Timestamp [UCT]: 2024-03-26 03:44:47 Age [y:d:h:m:s]: 01:238:10:23:46
Block: 986485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 429085 RingCT/type: yes/0
Extra: 01bb1fa71c6555ca930b5f532e4b689b43a5ef2e6eba1b69ca136f49fe3dbf614b02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea271abeadae940cee7cbdd44407531606dfbd9346887e5aad286406a7be0517 0.600000000000 1446714 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": 986495, "vin": [ { "gen": { "height": 986485 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea271abeadae940cee7cbdd44407531606dfbd9346887e5aad286406a7be0517" } } ], "extra": [ 1, 187, 31, 167, 28, 101, 85, 202, 147, 11, 95, 83, 46, 75, 104, 155, 67, 165, 239, 46, 110, 186, 27, 105, 202, 19, 111, 73, 254, 61, 191, 97, 75, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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