Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90d22990f4943b0ad16cca1f1f227ed8b81a00c720a1d191531f7e56b7c52f4a

Tx prefix hash: 0af23fbbc74e807453353c2daf5adafdc4f6e4dca943b955b2925519cdc8bc14
Tx public key: 5e3868864d50a9dc39af74ae6fc2a08399f42265fb2dee72aa93b9035efa5cde
Timestamp: 1710548315 Timestamp [UCT]: 2024-03-16 00:18:35 Age [y:d:h:m:s]: 01:003:22:39:59
Block: 979217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263802 RingCT/type: yes/0
Extra: 015e3868864d50a9dc39af74ae6fc2a08399f42265fb2dee72aa93b9035efa5cde02110000000139e1d5d3000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 680d7dd8b37e43ab5dc121a8d8efae1d4ae1caeb8a96264b085acb30cccae10e 0.600000000000 1439250 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": 979227, "vin": [ { "gen": { "height": 979217 } } ], "vout": [ { "amount": 600000000, "target": { "key": "680d7dd8b37e43ab5dc121a8d8efae1d4ae1caeb8a96264b085acb30cccae10e" } } ], "extra": [ 1, 94, 56, 104, 134, 77, 80, 169, 220, 57, 175, 116, 174, 111, 194, 160, 131, 153, 244, 34, 101, 251, 45, 238, 114, 170, 147, 185, 3, 94, 250, 92, 222, 2, 17, 0, 0, 0, 1, 57, 225, 213, 211, 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