Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 779796b33e8451b040ccfce520be115d930a7029f1577c48bd2912c2d8d69d39

Tx prefix hash: e03125a8a2316e6c51c654ae1381ddbafaa03fb5ecd02215cb31a80f9be5968c
Tx public key: c0c6ab4c0d43a62a69f4e045315da1ec4ef742eb2f3976017a477b8c4058b48c
Timestamp: 1710751126 Timestamp [UCT]: 2024-03-18 08:38:46 Age [y:d:h:m:s]: 00:255:06:16:08
Block: 980900 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182733 RingCT/type: yes/0
Extra: 01c0c6ab4c0d43a62a69f4e045315da1ec4ef742eb2f3976017a477b8c4058b48c02110000000e52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ccecb5945674768fe6a69c44486c2e98279bec7fd2eca4615a2951c183fa6c8 0.600000000000 1440985 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": 980910, "vin": [ { "gen": { "height": 980900 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ccecb5945674768fe6a69c44486c2e98279bec7fd2eca4615a2951c183fa6c8" } } ], "extra": [ 1, 192, 198, 171, 76, 13, 67, 166, 42, 105, 244, 224, 69, 49, 93, 161, 236, 78, 247, 66, 235, 47, 57, 118, 1, 122, 71, 123, 140, 64, 88, 180, 140, 2, 17, 0, 0, 0, 14, 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