Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 564334adddda8e21adb398a67e572075ac58b0f0668bbf6d202a623932240d4d

Tx prefix hash: 2d86ac0a19ddefd3481b889c252f0f3d8fe5b0711f50106b6b23f9dd1d668d5a
Tx public key: e2dd1ddcafb13868a7307915f8f450146d7d4fc6a362f2bd9d1cbfe2cef0aec6
Timestamp: 1693846118 Timestamp [UCT]: 2023-09-04 16:48:38 Age [y:d:h:m:s]: 01:206:10:33:17
Block: 840911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408648 RingCT/type: yes/0
Extra: 01e2dd1ddcafb13868a7307915f8f450146d7d4fc6a362f2bd9d1cbfe2cef0aec602110000000533af99f4000000000000000000

1 output(s) for total of 1.003951766000 dcy

stealth address amount amount idx
00: c259ad8f2b278cad284a1fee96bee39dc278e97d28da245b535797a1e4d73370 1.003951766000 1293889 of 0

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": 840921, "vin": [ { "gen": { "height": 840911 } } ], "vout": [ { "amount": 1003951766, "target": { "key": "c259ad8f2b278cad284a1fee96bee39dc278e97d28da245b535797a1e4d73370" } } ], "extra": [ 1, 226, 221, 29, 220, 175, 177, 56, 104, 167, 48, 121, 21, 248, 244, 80, 20, 109, 125, 79, 198, 163, 98, 242, 189, 157, 28, 191, 226, 206, 240, 174, 198, 2, 17, 0, 0, 0, 5, 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