Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63235a20704f2aa801e9b9a7587d07dca139a8e64fa1455761a936592dc68d32

Tx prefix hash: ccd8bc177b6ac418a2601ebb57c2dc3d496553204a2d8234e951508c396938ae
Tx public key: feb1913e56e9be1b18d17be76b07d4a45393351252b478b6be7f55a65dbd0b59
Timestamp: 1714348986 Timestamp [UCT]: 2024-04-29 00:03:06 Age [y:d:h:m:s]: 00:247:18:39:05
Block: 1010698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177355 RingCT/type: yes/0
Extra: 01feb1913e56e9be1b18d17be76b07d4a45393351252b478b6be7f55a65dbd0b5902110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 096ae05996082d5df69d387b50cc63c6e2f54d9ae1480ab6c10633a3a72fbf6f 0.600000000000 1472728 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": 1010708, "vin": [ { "gen": { "height": 1010698 } } ], "vout": [ { "amount": 600000000, "target": { "key": "096ae05996082d5df69d387b50cc63c6e2f54d9ae1480ab6c10633a3a72fbf6f" } } ], "extra": [ 1, 254, 177, 145, 62, 86, 233, 190, 27, 24, 209, 123, 231, 107, 7, 212, 164, 83, 147, 53, 18, 82, 180, 120, 182, 190, 127, 85, 166, 93, 189, 11, 89, 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