Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83cb91e6f30314206be4f015ea1a3dee907613a0e2e2b0927fa107183abdf39c

Tx prefix hash: aad68628eb76d34ccf26f57bf6475e1cca341e40f11d1f6a1820feaace36dd1b
Tx public key: d2465abda4235dce990474796a42a4331a78b064dac836554bfc2f1868c83f2a
Timestamp: 1578072229 Timestamp [UCT]: 2020-01-03 17:23:49 Age [y:d:h:m:s]: 04:361:06:55:25
Block: 37860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1147499 RingCT/type: yes/0
Extra: 01d2465abda4235dce990474796a42a4331a78b064dac836554bfc2f1868c83f2a02110000000d8a2ee0d9000000000000000000

1 output(s) for total of 459.785164701000 dcy

stealth address amount amount idx
00: 0289b3d81fa7adbe27c00abdff852f0e10742e245c483519638a9acd5110e622 459.785164701000 64389 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": 37870, "vin": [ { "gen": { "height": 37860 } } ], "vout": [ { "amount": 459785164701, "target": { "key": "0289b3d81fa7adbe27c00abdff852f0e10742e245c483519638a9acd5110e622" } } ], "extra": [ 1, 210, 70, 90, 189, 164, 35, 93, 206, 153, 4, 116, 121, 106, 66, 164, 51, 26, 120, 176, 100, 218, 200, 54, 85, 75, 252, 47, 24, 104, 200, 63, 42, 2, 17, 0, 0, 0, 13, 138, 46, 224, 217, 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