Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05628b93fa8e56ca311156a7e4477b431b49dcb382177b33e11b4490527e857d

Tx prefix hash: c299afc9d2b2eef5b7a55550f5a0ac46c97cc80e83e4dd353dbd7fc27dfbdd0c
Tx public key: 10e958228e05c0a797d8762620073d9aaee6a091d4a708eef2d78a6f944e5ada
Timestamp: 1671417464 Timestamp [UCT]: 2022-12-19 02:37:44 Age [y:d:h:m:s]: 02:027:07:49:33
Block: 655670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 541440 RingCT/type: yes/0
Extra: 0110e958228e05c0a797d8762620073d9aaee6a091d4a708eef2d78a6f944e5ada02110000000a75e3f0e9000000000000000000

1 output(s) for total of 4.125656696000 dcy

stealth address amount amount idx
00: cc69fc032364f0ba4b59f11fd73eba7d292fe032e9e0b1e7843387d20d315eeb 4.125656696000 1096233 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": 655680, "vin": [ { "gen": { "height": 655670 } } ], "vout": [ { "amount": 4125656696, "target": { "key": "cc69fc032364f0ba4b59f11fd73eba7d292fe032e9e0b1e7843387d20d315eeb" } } ], "extra": [ 1, 16, 233, 88, 34, 142, 5, 192, 167, 151, 216, 118, 38, 32, 7, 61, 154, 174, 230, 160, 145, 212, 167, 8, 238, 242, 215, 138, 111, 148, 78, 90, 218, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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