Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 391d7c62324e26e4a4abd725cb45fc742562ca27731641ae29d1c842524671d6

Tx prefix hash: 1418ce61e4bcc9780b5f1614c1069c8d3be5327c11c723a7a65aaf4b2347ba9a
Tx public key: 37834a00f99a81d2ae438626f56d9f127b64538ad5115c8fb22a30a3689e2b19
Timestamp: 1702219876 Timestamp [UCT]: 2023-12-10 14:51:16 Age [y:d:h:m:s]: 01:120:21:06:01
Block: 910144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347544 RingCT/type: yes/0
Extra: 0137834a00f99a81d2ae438626f56d9f127b64538ad5115c8fb22a30a3689e2b1902110000000833af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a5f3125df638a2582c6d7ea471c844eca35eeb0f0018041e8e944c4424b8af4 0.600000000000 1367289 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": 910154, "vin": [ { "gen": { "height": 910144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a5f3125df638a2582c6d7ea471c844eca35eeb0f0018041e8e944c4424b8af4" } } ], "extra": [ 1, 55, 131, 74, 0, 249, 154, 129, 210, 174, 67, 134, 38, 245, 109, 159, 18, 123, 100, 83, 138, 213, 17, 92, 143, 178, 42, 48, 163, 104, 158, 43, 25, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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