Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac2f727d3b98108ffd58d643dc6672b498d5f843e15e71c58a27ea995be164da

Tx prefix hash: c6b460d7bbe86c25d6115c6b34e5b66428dcc02cfc266d9ede602b9fa4dacb0a
Tx public key: 5400cf13938fe16536209c266fb77aa845be313d297017d8fff4a870c2a42148
Timestamp: 1750006647 Timestamp [UCT]: 2025-06-15 16:57:27 Age [y:d:h:m:s]: 00:155:06:51:16
Block: 1305664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108764 RingCT/type: yes/0
Extra: 015400cf13938fe16536209c266fb77aa845be313d297017d8fff4a870c2a42148021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 898453cb5609a00c1f84c69591dbf13ed77ba4e12fc0f1d239e5ec3f241fdc41 0.600000000000 1793265 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": 1305674, "vin": [ { "gen": { "height": 1305664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "898453cb5609a00c1f84c69591dbf13ed77ba4e12fc0f1d239e5ec3f241fdc41" } } ], "extra": [ 1, 84, 0, 207, 19, 147, 143, 225, 101, 54, 32, 156, 38, 111, 183, 122, 168, 69, 190, 49, 61, 41, 112, 23, 216, 255, 244, 168, 112, 194, 164, 33, 72, 2, 17, 0, 0, 0, 3, 191, 81, 178, 162, 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