Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 978b27eb2dbceaadce051d4eee3b782b002d56281db20d551785270d0fc9e43d

Tx prefix hash: df3edb45f1682ab73c3bf3e8b6f84188f6bf81237b10df15b49b377df845f8ba
Tx public key: ada9fe95f4c90901e0f5de0fd12b71b68794422d3e229aa5e51097067223444c
Timestamp: 1730276140 Timestamp [UCT]: 2024-10-30 08:15:40 Age [y:d:h:m:s]: 00:228:09:45:06
Block: 1142680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163014 RingCT/type: yes/0
Extra: 01ada9fe95f4c90901e0f5de0fd12b71b68794422d3e229aa5e51097067223444c021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3f0b322f16053ccf475200861fa94a77e69acbc0eccd49a88b76e86e9695b87 0.600000000000 1626535 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": 1142690, "vin": [ { "gen": { "height": 1142680 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3f0b322f16053ccf475200861fa94a77e69acbc0eccd49a88b76e86e9695b87" } } ], "extra": [ 1, 173, 169, 254, 149, 244, 201, 9, 1, 224, 245, 222, 15, 209, 43, 113, 182, 135, 148, 66, 45, 62, 34, 154, 165, 229, 16, 151, 6, 114, 35, 68, 76, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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