Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9ce2580ff74c52b08eee65ac6dc7d349464d2417f73cc86de98f95c8d28dd9a

Tx prefix hash: 399e0c610ab577194a1b07cc7dcb7671391d40fb75e731e3ec262ae364c772ed
Tx public key: f42a0da1401ef92ca9d6f60153a71281c38f6f3a16281559a330f11e8bfb180b
Timestamp: 1727255138 Timestamp [UCT]: 2024-09-25 09:05:38 Age [y:d:h:m:s]: 00:094:02:44:50
Block: 1117704 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67284 RingCT/type: yes/0
Extra: 01f42a0da1401ef92ca9d6f60153a71281c38f6f3a16281559a330f11e8bfb180b02110000001d91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6405b03abc9c8222540672b6ede9c6d975d6339cda8fa120cabcc8296386f6f2 0.600000000000 1598639 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": 1117714, "vin": [ { "gen": { "height": 1117704 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6405b03abc9c8222540672b6ede9c6d975d6339cda8fa120cabcc8296386f6f2" } } ], "extra": [ 1, 244, 42, 13, 161, 64, 30, 249, 44, 169, 214, 246, 1, 83, 167, 18, 129, 195, 143, 111, 58, 22, 40, 21, 89, 163, 48, 241, 30, 139, 251, 24, 11, 2, 17, 0, 0, 0, 29, 145, 225, 60, 4, 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