Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cf5e133d9923633b292b1e52e535cc3bbc51093cea1775f828f0996eecdc09f

Tx prefix hash: 440f9f079ac36ed1796a084b82160a1eed8c5cb53535bd423aafb59e12010e97
Tx public key: 27931e692cdc1598cc0e1d5e04e77cf7662fe6c4e42905b944a839d447ea589a
Timestamp: 1723813225 Timestamp [UCT]: 2024-08-16 13:00:25 Age [y:d:h:m:s]: 00:303:09:14:03
Block: 1089173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216640 RingCT/type: yes/0
Extra: 0127931e692cdc1598cc0e1d5e04e77cf7662fe6c4e42905b944a839d447ea589a021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2e62532309aaf7ee245ca1edec9393c7d0ba1d335966ae49f34999836bcbf2a 0.600000000000 1563792 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": 1089183, "vin": [ { "gen": { "height": 1089173 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2e62532309aaf7ee245ca1edec9393c7d0ba1d335966ae49f34999836bcbf2a" } } ], "extra": [ 1, 39, 147, 30, 105, 44, 220, 21, 152, 204, 14, 29, 94, 4, 231, 124, 247, 102, 47, 230, 196, 228, 41, 5, 185, 68, 168, 57, 212, 71, 234, 88, 154, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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