Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9844a23fd4584e74ada3ccb8578004f0f070a44d3fc2a1c9e1f58fa4384ea20b

Tx prefix hash: 9074060eedce3ac07baab15e3f3e5dcda05d036d78608bee0910daef61e7ceb7
Tx public key: 5695c8cdc239b37031471f1434a503edd1570704c820c9c2f50953bd9d2fefeb
Timestamp: 1723273925 Timestamp [UCT]: 2024-08-10 07:12:05 Age [y:d:h:m:s]: 00:239:20:12:51
Block: 1084703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171283 RingCT/type: yes/0
Extra: 015695c8cdc239b37031471f1434a503edd1570704c820c9c2f50953bd9d2fefeb021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50e2d4cbeb2b2949bf4805e8dac574e317a5fd60f6082efcdeaffc389d27f15a 0.600000000000 1559074 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": 1084713, "vin": [ { "gen": { "height": 1084703 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50e2d4cbeb2b2949bf4805e8dac574e317a5fd60f6082efcdeaffc389d27f15a" } } ], "extra": [ 1, 86, 149, 200, 205, 194, 57, 179, 112, 49, 71, 31, 20, 52, 165, 3, 237, 209, 87, 7, 4, 200, 32, 201, 194, 245, 9, 83, 189, 157, 47, 239, 235, 2, 17, 0, 0, 0, 4, 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