Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2763d1a80a1f0a6b35daec6375ada81385ba0410baba8eb6ef4c36d59114e9bd

Tx prefix hash: 08ef0725f62287a8e96f82d91dcccd33e4b131757d2f46573b19f2fb23ff1cb9
Tx public key: 9fccb27a4b45d11fa14158146a7ff90982eb811c95c1ca843eda84d7ea6eb28b
Timestamp: 1736443133 Timestamp [UCT]: 2025-01-09 17:18:53 Age [y:d:h:m:s]: 00:341:13:01:40
Block: 1193737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241644 RingCT/type: yes/0
Extra: 019fccb27a4b45d11fa14158146a7ff90982eb811c95c1ca843eda84d7ea6eb28b0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78b5e1a734208bd3960e34c59f26f0b3ac01b359046f03c0e6bbd4be1a8c9d94 0.600000000000 1680302 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": 1193747, "vin": [ { "gen": { "height": 1193737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78b5e1a734208bd3960e34c59f26f0b3ac01b359046f03c0e6bbd4be1a8c9d94" } } ], "extra": [ 1, 159, 204, 178, 122, 75, 69, 209, 31, 161, 65, 88, 20, 106, 127, 249, 9, 130, 235, 129, 28, 149, 193, 202, 132, 62, 218, 132, 215, 234, 110, 178, 139, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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