Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc8947a7816a29c77642a7d53ed5256868509efdeadb67561de20039681d367e

Tx prefix hash: c2a93970bf29e0afcf54941984e103d6b580982eddf9bc4fa6597d34c4ee79d3
Tx public key: 3a77da6d0164fcf8d79a540e2315fe843f02e4034e14c4c0dd53c954c1fefa2c
Timestamp: 1704861536 Timestamp [UCT]: 2024-01-10 04:38:56 Age [y:d:h:m:s]: 01:304:09:30:20
Block: 932032 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476382 RingCT/type: yes/0
Extra: 013a77da6d0164fcf8d79a540e2315fe843f02e4034e14c4c0dd53c954c1fefa2c0211000000019da8e134000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a828c5fe7137a0f2c15fa1d3facdf277b69e61794709d7d225f7a6dbcff0f322 0.600000000000 1389944 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": 932042, "vin": [ { "gen": { "height": 932032 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a828c5fe7137a0f2c15fa1d3facdf277b69e61794709d7d225f7a6dbcff0f322" } } ], "extra": [ 1, 58, 119, 218, 109, 1, 100, 252, 248, 215, 154, 84, 14, 35, 21, 254, 132, 63, 2, 228, 3, 78, 20, 196, 192, 221, 83, 201, 84, 193, 254, 250, 44, 2, 17, 0, 0, 0, 1, 157, 168, 225, 52, 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