Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8cd31925f0a513d48590dcee174803190c66e3d7c4d4a82adf3ef0c0cc63d86

Tx prefix hash: 6ff1ca50cbc7b46357d172d755b27e0ff79e5635c51473c352c6763cca19519d
Tx public key: 079777526e132285e1986b1f141aba7f11dd8e4ceb626b5971a516825b6bb302
Timestamp: 1699804955 Timestamp [UCT]: 2023-11-12 16:02:35 Age [y:d:h:m:s]: 01:155:17:36:08
Block: 890136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372489 RingCT/type: yes/0
Extra: 01079777526e132285e1986b1f141aba7f11dd8e4ceb626b5971a516825b6bb302021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.689620109000 dcy

stealth address amount amount idx
00: a246b2ce1660cbd73c82d14debf776b9c4d069dfd18382ceb950532e9c252967 0.689620109000 1346155 of 0

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": 890146, "vin": [ { "gen": { "height": 890136 } } ], "vout": [ { "amount": 689620109, "target": { "key": "a246b2ce1660cbd73c82d14debf776b9c4d069dfd18382ceb950532e9c252967" } } ], "extra": [ 1, 7, 151, 119, 82, 110, 19, 34, 133, 225, 152, 107, 31, 20, 26, 186, 127, 17, 221, 142, 76, 235, 98, 107, 89, 113, 165, 22, 130, 91, 107, 179, 2, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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